-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: improve logging #690
Conversation
35ed8b9
to
8ff4d05
Compare
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
"height", stateData.Height, | ||
"round", stateData.Round, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did we remove height and round?
@@ -395,10 +395,10 @@ func (blockExec *BlockExecutor) ValidateBlockWithRoundState( | |||
// Validate app info | |||
if uncommittedState.AppHash != nil && !bytes.Equal(block.AppHash, uncommittedState.AppHash) { | |||
return fmt.Errorf( | |||
"wrong Block.Header.AppHash at state height %d, block %d. Expected %X, got %X", | |||
"Block.Header.AppHash mismatch; state (or ABCI App) at height %d expects App Hash %X, block at height %d expects App Hash %X", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my perspective, the new message is more confusing than the previous one. What if we just swap app hash params and keep the old one?
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue being fixed or feature implemented
Logs are too verbose
What was done?
How Has This Been Tested?
Github Actions
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only